Note this article is still a WIP. Peter to finalize as the New Installer is now settled prior to end of August.

this is all new in 23.3 RC1 from the Lumion side - see also mention by Marius below

nice reply by Javier for a std reply for any multi-user cant use the Updater to silently install Updates

Thanks for contacting us.

Sorry to hear about this. I completely understand your concerns about the time-consuming nature of coordinating with non-admin users individually for updates.

At present, a multi-user silent update installation (with no admin rights) is not possible, unfortunately, but it is on the development plan:

In the interim, you can do the following:

1. Whenever a new Lumion 2023 version comes out, you can download it from your Lumion Account on a single PC.

2. To streamline the process for multi-user installations, you can deploy a Silent Install of the newest version from that PC to all the others:

This is a temporary workaround until a solution becomes available.

We appreciate your understanding as we work towards enhancing the update and installation experience for our users.

If you have further questions or require assistance with any of the steps mentioned above, please don't hesitate to reach out to us.
===

this error (Running in update000 but no flags were set to be in update download or update install mode.) is when you manually start the update000.exe from within the Lumion installation folder.

Correct me if I'm wrong @Danny van den Bree
When Lumion download updated and start the update installation it sets multiple arguments. This ofcourse doesn't happen when you just start update000.exe manually

Danny van den Bree, Yesterday 11:05 PM
That is indeed what happens when you start update000.exe manually without the install or update flag. I've added the error(10353) on the excel sheet.

updated EKB on error type: section 16. Installer (Update process) - no flags were set.

and the Learn More message is not available when Updater cannot install (Installer 3.22)

"there is an update.. its downlaods.. installs, gets to the end, says update complete, but underneath it says unable to install update in a red box.. and the learn more is crossed out"

We have reproduced this issue by logging on 2 account on 1 machine. Open browser on 1 account, leave it open and log on the second account. Starting the browser won't work on the second user because it's already in use by the first user. This works the same for the DM. And because of this Windows limitation, it cannot be fixed.

having 2 accounts logged in, is not recommended (but it should not have any effect on the installation itself). I don’t think the DM is able to tell if more than one user is logged in.

Ask the user to log out of all Windows Accounts and only log in again on the account they want to use with Lumion and then try the Update again.

this is different from the set as Admin which resolves in most cases the Updater not able to start the Install process.

There are a few things we can try so let's take it step by step:

1.  In Windows File Explorer go to the main folder C:\ProgramData.

2.  If there is a folder named LumionUpdater use Shift+Delete to remove it. If there is none, please just continue with step 3.

3. Then manually create a new folder LumionUpdater.

4.  In that folder create a new folder lum23pro.

5.  In the folder C:\ProgramData\LumionUpdater\lum23pro save the attached file: update.ini - extract it from the archive.

6. Add exclusions in your antivirus for:

7. Reboot the PC and start the Pro version of Lumion again.
8. After that, close Lumion Pro, reboot the PC, repeat steps 1. to 5. and start Lumion Standard.

This should give everything a fresh start to ensure that nothing is interfering with the updates and you don't end up with a partial installation.

THESE ARE A FEW NOTES ON RELEASE 2023 AND THE NEW UPDATER FOR PART OF THE INTENRAL SUPPORT

Dimitris Sifakis, 6:24 AM, Edited
another follow up question:
where are the updater files being stored before installation?

if there is a problem with files not fully downloading - apart form assessing the logfile.txt file

then it might work to get user to delete all folders/files to start the download again from scratch (it worked only as a test to see how the Updater handles things for a non or limited download scenario)

Note: maybe we should mention the new installer in the 12.3 release notes, just as a record.

Danny van den Bree, 1:44 AM
When you have tickets like these: https://lumion.zendesk.com/agent/tickets/31467
Always ask for logfile.txt, the error code you see in interface may not be the exact reason why it fails. For example, when 7z fails to copy because of limited access to folder it will still trigger this error code because not all files were installed in the target folder. And has nothing to do with diskspace, keep that in mind ;)

Peter: for the moment, Always ask for logfile.txt. The purpose of the error messages and tied in articles as such, and especially if go the next level is to get more direct resolution at the user level - user follows and resolved- of course, why not, and the logfile is our door to full events of the download and install for resolution.

1. See Floyds Plan B end of this article for fallback to the other older Installer if all else fails

2. The new EKBs are still rough around the edges. There was a last-minute revision on the original approach we could take but hopefully, that might happen a little later on with a change Danny can implement - relates to how the Installer interfaces with the support articles and how we channel those articles.

3. You should be able to use the new four EKBs (2 main and 2 other bits articles) along with the GSheet that shows the error codes and messages, especially for help in following what will be in the logfile.txt log file.

4. The Installer will throw an error that results in the final UI message with a button to click to get Help and links as in the sheet to one of the four articles.

5. The EKBs have needed to be structured where in some cases there are 4 or 5 different errors (error codes) that all get lumped back to the same user message in the Installer. Unfortunate but that's as it is for the meantime.

That might be or seem a bit confusing or too much there but it won't harm (yeah right) but first cut to also include some of the enhanced pathway this could be done as has also been included. If needed some that have a Note about checking each same Error Message can be consolidated. But please work with it.

The article structure is weighted toward the individual error types where in the future it should be more possible for both the user and us to more specifically pinpoint an exact error type/code and give a more direct fix.

The EKBs probably will need some more restructuring for the current pathway. And yet to add some example screenshots of error UI screens.

Users may still be using the old Download Manager and old Installer -> old EKB articles as before - same article link

So the first thing you need to do is determine what version of Lumion they are downloading as the New V2.0 Installer only applies to V12.3+.

Most of the issues are still common to both - re our majors of AV and permissions.

Installer V2.0 replaces both the n(new) Download Manager and the (old) Installer with a single unified interface and file for both parts of the process. The installation and setup verification processes are now much faster.

The existing Download Manager and Installers will still be active for older versions of Lumion given there are also old emails with links that activate the old or current (to be old) DLM and Installer.

When the Download Manager is started, it will request an Activation Code (unless the download webpage is active) and create a cache file in its location. This cache file is necessary for the download and installation to proceed and should not be removed. If it is removed for some reason, the Download Manager will attempt to create it again upon launch.

The Download Manager allows for 6 attempts to enter the correct Activation Code correctly, otherwise, it will lock itself for (15?) minutes. If entered correctly, the Lumion installation files will automatically begin to download to the location in which the Download Manager was started in (which is usually the Downloads folder in the C: drive.).

If for some reason the download is paused or canceled, the Download Manager can be resumed later and will verify which files have been downloaded so far and continue the download from there when it started again. If any files are removed, the downloader will attempt to redownload them.

At this point, Lumion needs at least 25GB of free space to download the files and will need another 40GB to install them.

Once all the installation files have been downloaded, the Lumion installer will start and request a folder location to install Lumion. The default folder will be C:\Program Files\Lumion.

Note that it is not possible to install Lumion to a root folder. If the default folder is not selected, an installation folder will need to be created manually.

After the installation has been completed, the installation files can be safely deleted.

Lumion can be uninstalled from Apps & Features, or by running the uninstall000.exe in the installation folder.

More info on how the cache file works can be found in this ticket: https://lumion.zendesk.com/agent/tickets/38679

Lumion requires admin rights to be installed. Even if it is not run as administrator, the Lumion installer will ask for elevated rights when the installation begins.

It's important that the installer is not started inside a network drive/server location. [that is: the user needs to start it on a PC so that the required files such as .cache can be correctly downloaded]

It's still possible to deploy a silent installation of Lumion 12.3.1.

For background, the new Download Manager in 12.3 is a unified installer. It uses the same Lumion_12_3_Download.exe to download and install the installation files.

You should be able to install Lumion on multiple PCs using the same installation files as long as you also copy the Lumion_12_3_Download.cache file together with all the archives that the installer needs. After running it again, the installer will verify the setup files and you should be good to go.

Note that the silent installation method is meant for installing Lumion only, not for downloading. Please download all the installation files first and then deploy the silent installation.

Follow the steps in this article to learn how:

1. make sure they have the latest Installer file Lumion_12_3_1_Download.exe

2. simply follow the article - it works for others

3. The files only need downloading once but the Installer file needs to run for each PC with the commands either via accessing the installation files from a server or copied locally and then installed.

4. The Activation Code is only needed the one time when downloading the installation files.

The errors are divided in what part of the installer code the error happened.
For example, errors starting with 00xxx happen in the part that handles the input of the activation code, 50xxx is the part that handles the download, 10xxx are the errors in the core system. So this division is purely based on the different cpp files Danny has written for the installer.

Error text interface: This is the error text that is shown in the installer when it encounters an error. This text can cover more than 1 error code.

however, with the errors shown in the log it should be more narrowed down so in theory we'd know exactly where to look

error code 114 will never happen in silent mode because it won't check if activation code is valid. It only checks for if the file exists. .000, 001 and .cache.

This error (10456) can happen in interface and in silent mode. In interface mode when you press "Start installation" it will check if all files are there and also the cache. If not, installation cannot continue and you need to restart the DM to create a new cache.

12:41:23 | 17-02-2022 -> (Init Pre completed with flags enabled: Silent(0) Installonly(0) IncludeSubVersion(0)) - File: F:\_CODE\Lumion_Downloader\Source\main.cpp - Line: 21	
12:41:24 | 17-02-2022 -> (Next window state: LOADING_APP) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1316	
12:41:25 | 17-02-2022 -> (Interface started.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1328	
12:41:25 | 17-02-2022 -> (Cache loaded.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1344	
12:41:25 | 17-02-2022 -> (Textures uploaded to GPU.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1371	
12:41:26 | 17-02-2022 -> (Next window state: ENTER_PRODUCTKEY) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1316	
12:41:30 | 17-02-2022 -> (Checking license...) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreDownload.cpp - Line: 81	
12:41:30 | 17-02-2022 -> (FileUpload::ServerSettingsFromUrl: https://downloadmanager.lumion3d.net/Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 572	
12:41:30 | 17-02-2022 -> (Disconnecting Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 349	
12:41:30 | 17-02-2022 -> (Opening connection for: Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 251	
12:41:30 | 17-02-2022 -> (InternetConnect downloadmanager.lumion3d.net 443) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 300	
12:41:30 | 17-02-2022 -> (Sending HTTP POST Headers:
Accept-Encoding: gzip,deflate
ActivationCode: DXCDGVDG
ComputerId: 3d432b03d14cd70312c3ccafac378b9c094a2185
Content-Type: application/x-www-form-urlencoded
Method: RequestDownload
User-Agent: Lumion Download Manager / 9.5) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 84	
12:41:31 | 17-02-2022 -> (HTTPSendRequest response headers:
HTTP/1.1 200 OK
Date: Thu, 17 Feb 2022 11:41:31 GMT
Content-Type: application/json; charset=us-ascii
Connection: keep-alive
CF-Ray: 6deebf400c629043-FRA
Cache-Control: private
Set-Cookie: ARRAffinity=2ffcedd6130e0eb275479b88a8a4332d13dee9e85629d376f936e98c038facff;Path=/;HttpOnly;Secure;Domain=downloadmanager.lumion3d.net
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Set-Cookie: ARRAffinitySameSite=2ffcedd6130e0eb275479b88a8a4332d13dee9e85629d376f936e98c038facff;Path=/;HttpOnly;SameSite=None;Secure;Domain=downloadmanager.lumion3d.net
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Server: cloudflare
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 175	
12:41:31 | 17-02-2022 -> (Disconnecting Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 349	
12:41:31 | 17-02-2022 - Code: 114 -> (The activation code you entered is not valid.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreDownload.cpp - Line: 119	
12:41:35 | 17-02-2022 -> (Verify pressed by user.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 212	
12:41:35 | 17-02-2022 -> (Checking license...) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreDownload.cpp - Line: 81	
12:41:35 | 17-02-2022 -> (FileUpload::ServerSettingsFromUrl: https://downloadmanager.lumion3d.net/Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 572	
12:41:35 | 17-02-2022 -> (Disconnecting Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 349	
12:41:35 | 17-02-2022 -> (Opening connection for: Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 251	
12:41:35 | 17-02-2022 -> (InternetConnect downloadmanager.lumion3d.net 443) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 300	
12:41:35 | 17-02-2022 -> (Sending HTTP POST Headers:
Accept-Encoding: gzip,deflate
ActivationCode: GBGKSRT2
ComputerId: 3d432b03d14cd70312c3ccafac378b9c094a2185
Content-Type: application/x-www-form-urlencoded
Method: RequestDownload
User-Agent: Lumion Download Manager / 9.5) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 84	
12:41:35 | 17-02-2022 -> (HTTPSendRequest response headers:
HTTP/1.1 200 OK
Date: Thu, 17 Feb 2022 11:41:35 GMT
Content-Type: application/json; charset=us-ascii
Connection: keep-alive
CF-Ray: 6deebf5b0ba99043-FRA
Cache-Control: private
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Server: cloudflare
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 175	
12:41:35 | 17-02-2022 -> (Disconnecting Lumion/DownloadManager8.ashx) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileUpload.cpp - Line: 349	
12:41:35 | 17-02-2022 -> (Activation code verified, starting download...) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 218	
12:41:35 | 17-02-2022 -> (Next window state: RUNNING_DOWNLOAD) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1316	
12:41:35 | 17-02-2022 -> (Lumion download started.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1454	
12:41:35 | 17-02-2022 -> (Opening connection: product-download-storage-v2.lumion3d.net) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 343	
12:41:35 | 17-02-2022 -> (Response headers: HTTP/1.1 200 OK
Date: Thu, 17 Feb 2022 11:41:36 GMT
Content-Type: text/plain; charset=UTF-8
Content-Length: 211
Connection: keep-alive
Last-Modified: Wed, 16 Feb 2022 08:50:03 GMT
ETag: "620cbabb-d3"
Cache-Control: public, max-age=0, s-maxage=31556952
X-Accel-Expires: @1676576428
Server: CDN77-Turbo
X-77-NZT: AcO1pA3ptH7/HDMBAA
X-77-NZT-Ray: bAjfuC57HDk
X-Cache: HIT
X-Age: 78620
X-77-POP: londonGB
X-77-Cache: HIT
Accept-Ranges: bytes

) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 431	
12:41:35 | 17-02-2022 -> (Finished file: ) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 89	
12:41:35 | 17-02-2022 -> (No CRC checked) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 118	
12:41:35 | 17-02-2022 -> (Download:  correct CRC. Download succesful.) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 151	
12:41:35 | 17-02-2022 -> (Opening connection: product-download-storage-v2.lumion3d.net) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 343	
12:41:35 | 17-02-2022 -> (Response headers: HTTP/1.1 200 OK
Date: Thu, 17 Feb 2022 11:41:36 GMT
Content-Type: text/plain; charset=UTF-8
Content-Length: 211
Connection: keep-alive
Last-Modified: Wed, 16 Feb 2022 08:50:03 GMT
ETag: "620cbabb-d3"
Cache-Control: public, max-age=0, s-maxage=31556952
X-Accel-Expires: @1676576428
Server: CDN77-Turbo
X-77-NZT: AcO1pA2DM97/HDMBAA
X-77-NZT-Ray: StwuGyiFxN4
X-Cache: HIT
X-Age: 78620
X-77-POP: londonGB
X-77-Cache: HIT
Accept-Ranges: bytes

) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 431	
12:41:35 | 17-02-2022 -> (Finished file: ) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 89	
12:41:35 | 17-02-2022 -> (No CRC checked) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 118	
12:41:35 | 17-02-2022 -> (Download:  correct CRC. Download succesful.) - File: F:\_CODE\Lumion_Downloader\Source\DownloadSystem\FileDownload.cpp - Line: 151	
12:41:45 | 17-02-2022 -> (Next window state: ENTER_INSTALLATION_INFO) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1316	
12:41:45 | 17-02-2022 -> (Lumion bin file data statistics retrieved.) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1480	
12:41:45 | 17-02-2022 -> (Failed to open registry key: Software\Microsoft\Windows\CurrentVersion\Uninstall\Lumion_12.0_Trial_Test) - File: F:\_CODE\Lumion_Downloader\Source\System\Registry.cpp - Line: 38	
12:41:49 | 17-02-2022 -> (Installation started by user while target folder is not empty: C:\Program Files\Lumion 12.0 Trial Test) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 501	
12:41:49 | 17-02-2022 -> (Next window state: RUNNING_INSTALLATION) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1316	
12:41:49 | 17-02-2022 -> (Starting installation of Lumion 12.0.2) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1493	
12:41:51 | 17-02-2022 -> (Installation cancelled activated by user!) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 559	
12:41:51 | 17-02-2022 -> (Next window state: INSTALLATION_FINISHED) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreInterface.cpp - Line: 1316	
12:41:52 | 17-02-2022 - Code: 10546 -> (Installation is cancelled!) - File: F:\_CODE\Lumion_Downloader\Source\CoreSystems\CoreSystem.cpp - Line: 574

logfile2.txt

Displaying logfile2.txt.

-----------------

Floyd: in Group room

Floyd van den Wijngaard

Yesterday 11:19 PM

@all about the new installer. Of course we hope the new installer won't cause any issues for our users. But if some users are walking into issues, that we can't resolve, we have the inno setup version as backup. In those situations send the suitable v2_dm.exe (they are available in the beta room) directly to the affected user. In the situation that shit really hits the fan, Arthur can swap the download in account.lumion.com to the innosetup. (The download url in the already sent emails will still point to the new installer). Of course we will resolve any issue with the new installer as quick as possible, and update the installer on the server

see Dimitris? prepared a (draft) article on this: https://lumion-knowledgebase.zendesk.com/knowledge/articles/4487108426514/en-us?brand_id=360001426299

Floyd van den Wijngaard

Yesterday 11:43 PM

In those situations send the suitable v2_dm.exe (they are available in the beta room) directly to the affected user Btw, don't give the user the url, but really send the dm.exe itself. (But I think that is something we do already if we need to share a specific DM with a user)

---------------------------------

from Danny: 6 April 2022

GDoc: https://docs.google.com/document/d/1ZAL-QV7Yb3cJtyaktxd3kuwwvUWpiL3q775eL32eh7Y/edit#

New Installer (v2.40.1)

Improved silent installation

There were some limitations with the new installer that prevented using it efficiently in deployment software. This has now been addressed in installer v2.40.1:

Added option to set a custom installation folder when installing in silent mode.
Added option to auto exit a silent installation

The parameters are changed compared to the previous version v2.39 and older. We did use `/silent` to do a silent install. With v2.40.1 this has been changed, see the available arguments. Every parameter has a short and a long version. Short parameters are using a single dash, long parameters are using a double dash.

-s or --silentinstall; silent installation

-e or --silentautoexit; auto continue after a silent installation has finished

-d or --silentinstalldir; custom installation directory when doing a silent installation

Examples

Silent installation in the default location

`Lumion_12_3_1_Download.exe -s` or `Lumion_12_3_1_Download.exe --silentinstall`

This will perform a silent install in the default location `c:\program files\Lumion 12.3`. When the installation is finished the user needs to press a key to continue

Auto continue after silent installation

`Lumion_12_3_1_Download.exe -s -e` or `Lumion_12_3_1_Download.exe --silentinstall --silentautoexit`

This will perform a silent install in the default location `C:\program files\Lumion 12.3`. When the installation is finished the installer will automatically exit

Silent installation in a custom directory

`Lumion_12_3_1_Download.exe -s -d “x:\custom”` or `Lumion_12_3_1_Download.exe --silentinstall --silentinstalldir “x:\custom”`

This will perform a silent install in the custom location “x:\custom”. When the installation is finished the user needs to press a key to continue

Note:

Our new installer doesn't uninstall Lumion installations that used the Inno setup version (Lumion_12_3_1_v2_download.exe). Please advise users that were given the Inno setup version, to manually uninstall that version before using this new version. Especially if they want to install this version in the same location they previously used.

Other changes in v2.40.1

Using the installer with the user interface. When the user selects the root of a drive, instead of giving an error, the installer will automatically add a Lumion installation folder.

For example, the user selects the “X:\” drive as custom installation location. Then the installer will automatically set the custom installation location to “X:\Lumion 12.3”.

-------------------------------------

Silent install prompts for Activation Key

https://lumion.zendesk.com/agent/tickets/34786

from the Installer 2.0 Gchat room:

Javier:

Any idea why a silent deploy would fail and display the error message

Error 65542: WGL: The driver does not appear to support OpenGL

Danny:

Did you check the log file that the installer was actually started in silent mode? Because in silent, OpenGL doesn't get started at all.

-------------------------------

Updated Installer version: 2.40.6

GChat June 2022

from this case:

Unusual error message from the new Installer. Please advise
And can you see anything else in the log file or system specs that is causing this issue?
https://lumion.zendesk.com/agent/tickets/36842

why this error message

when Windows is Operating System: Windows 11 Pro for Workstations 64-bit (10.0, Build 22000) (22000.co_release.210604-1628)

So the logfile.txt will now also log the windows version:
14:33:01 | 21-06-2022 -> (Windows build: major(10) minor (0) build (19044)) - File: D:\_CODE\_LUMION\Lumion_Downloader_v2\Source\CoreSystems\CoreSystem.cpp - Line: 1429

If there is an issue with retrieving the windows version then there are three additional errors that are written in the logfile.txt
1: The cache file is empty: 101405 MinimalWindowsBuild string is empty
2: (Wrong/unsupported) Characters in the windows build: 101411 MinimalWindowsBuild has characters which cannot be used
3: When it doesn't return any windows version at all: 101423 Unable to retrieve build number

Updated to enable logging:

v.2.40.7 with force logging. In CMD, bat or shortcut add -l or --forcelogging

1. Extract the Installer in a folder.
2. Right-click the Lumion_12_5_Download.exe file -> Create shortcut
3. Right-click the shortcut -> Properties -> Shortcut Tab -> in the 'Target' field type: --forcelogging
Note: there is a space is required before the text string which is required after the ". It should look like this:

server t obe updated about 24/06/2022

Update 3 Jan 2024:

Please enable a setting called "force logging". Here's how:

1.1: Right-click the Lumion_2023_4_2_Download.exe file -> Show More Options (if needed) -> Create Shortcut.

1.2: Right-click the shortcut -> Properties -> Shortcut Tab -> in the 'Target' field type: --forcelogging

Note: there is a space required before the text string which is required after the ". It should look like this:

1.3: Use that shortcut to run the Download Manager/Installer.

And then attach the logfile.txt.

--------------------------------------

note:

thes build reference 17763 is latest build for the same Windows Version 1809

--------------------------------------------------

Installation Temp folder (per setupLumionCommercial.bat in the installation):

installation_temp_folder=C:\Users\[yourusername]\AppData\Local\Temp\LumionInstallerData

---------------------------------------------

Some extra info:

When Lumion is started for the first time, it will create a folder in the Documents folder.

Lumion needs at least 30GB of free space at all times on the drive that this folder is located in. This is crucial for Lumion to work properly, as explained in the article below:

Knowledge Base: Why does Lumion need access to your computer's Documents folder?

What is the purpose of each folder?

Group Library

Library: This is where the Imported Models data is stored whenever a 3D file is imported/Livesynced or when a .LS Project file containing them is loaded. The 3D model data is stored in 4 different Lumion proprietary formats:

LIB: Model vertex data
MTT: Material data, which includes custom user textures.
TXX: only the model imported (embedded) textures
INN: this contains the thumbnail of the model

Materials: This is where Custom Materials are saved.

Miscellaneous: Stores sound files and video textures.

Projects: AutoSaved files can be found here.

Recent:

---------------------------------------------------------------------------

Chat: Installer Room

Thursday 1 Sept 2022

Danny van den Bree

Thu 3:09 AM

Peter Mellor: Hi Danny If the Installer sees the primary display device as something like Microsofts' Basic Display Device then will it immediately fail/not run? And even if there is a valid dedicated card as a secondary device?

I'm selecting primary monitor, this is usually the monitor where elements like the task bar or global menu bar are located.

Danny van den Bree

Thu 3:15 AM

Peter Mellor: @Danny van den Bree or @Floyd van den Wijngaard In the notes on the New Installer we have some notes from elsewhereLumion requires admin rights to be installed. Even if it is not run as administrator, the Lumion installer will ask for elevated rights when the installation begins ...

Download manager checks if it's started as admin, you cannot elevate program while running, only works by restarting it (this is done by the DM itself on launch). Because of this limitation, the DM needs admin from the start even tho you want to download Lumion only.

Danny van den Bree

Thu 3:18 AM

Peter Mellor: @Danny van den Bree Installer V2: What domains are accessed for the download. ...

We only have 2 domains, 1 for commercial and 1 for the trial builds. This is selected based on activation code, this cannot be manipulated since this data comes from our API service directly. I don't know if the domains have backup servers when the first one cannot be reached, this is something you need to ask Arthur about.

-----------------------------

CRC Download failed from server.

https://lumion.zendesk.com/agent/tickets/47227

user unable to get sorted for any other way than this:

Finally I made it. Give up the wi-fi and connected directly to the modem, it worked!

-------------

on uninstall user may get this message: Unable to remove folder: platforms

Installer V2 Room:

Peter

Mar 20, 1:32 PM

, Edited

@Danny van den Bree Any idea why this message occurred for L23? after a user Uninstalled, the final message was Unable to remove folder: platforms nothing in our V2 GSheet on Error Codes https://lumion.zendesk.com/agent/tickets/50261

Floyd van den Wijngaard

Mar 20, 9:38 PM

Sounds like it couldn't delete the platforms folder

in the lumion installation dir

Floyd van den Wijngaard

Mar 20, 9:41 PM

Aks for the logfile.txt

Dimitris Sifakis

Mar 20, 9:41 PM

will do, floyd

thanks\

but i think that stage was overcome

that guy managed to install succesfully afterwards. probably just dllhost keeping files occupied? but if he comes back,. we'll ask

Floyd van den Wijngaard

Mar 20, 9:56 PM

Not sure if the logfile.txt is still in the installation folder after he was able to do a full (re-)install

Peter

Mar 20, 10:07 PM

Was wondering what the term "platform" referred to?

Floyd van den Wijngaard

Mar 20, 10:12 PM

It contains the qwindows.dll. That is part of QT, which is used for part of the interfaces in Lumion, like text boxes and input fields

And somehow is was in use or blocked by another process like Dimitris suggested

Peter

Mar 20, 10:14 PM

OK, Thanks.

Peter

3 min

I managed to replicate (by accident) the message: "Unable to remove folder: platforms" when Lumion has not completely shut down - still doing so in the background and all files have not been removed

and yes logfile.txt showed files not able to be removed:

logfile.txt

Peter

1 min

, Edited

will add to our IKB for this (soon)

====================================

Cannot install 12.5, cannot uninstall 23

https://lumion.zendesk.com/agent/tickets/51476

not the usual, log here only

Trying to install/uninstall, not getting anywhere. 
Installer loads Lumion Logo and then disappears without visible error or background process, 
uninstaller errors with "Cannot create output directory"
Cannot find the path specified D:\Temp\LumionInstallerData

I realized the issue is on my end. Windows' TEMP and TMP directories were pointing 
to a drive that no longer existed. 

After I changed that, the install is now working as intended.

=========================

Updater issues:

1. Issue: Looped Updating - not completing, Unable to Install Update

https://lumion.zendesk.com/agent/tickets/50977

it then says there is an update.. its downlaods.. installs, gets to the end, says update complete, but underneath it says unable to install update in a red box.. and the learn more is crossed out (you cant click it).
i reopen, and it doesnt recognsie the update install and asks me to download it again and repeat process

possible Solution:

The issue that you are seeing with the updater is most of the time caused by the antivirus software, unfortunately.

To fix that please try the following:

1. Add an antivirus exclusion for Lumion.exe and the LumionUpdate folder (C:\ProgramData\LumionUpdater):

Knowledge Base: How do you resolve anti-virus and firewall problems?

2. And a firewall exclusion for Lumion.exe. Instructions below:

Knowledge Base: How do you add an exclusion for Lumion in Windows Defender and Windows Firewall?

If you are using different antivirus software, the steps should be similar and easy to look up.

3. After that is done, run Lumion as an Administrator and try to update again.

-------------

2. Issue: Lumion not prompting for updates

https://lumion.zendesk.com/agent/tickets/51485

Solution?:

Lumion updates are delivered straight in the product. Only the main version will appear on the Lumion Account and updates needs to be installed after the main version.

Regarding the issue the user is facing, let's try a few things.

1. In Windows File Explorer go to the main folder C:\ProgramData.

2. If there is a folder named LumionUpdater use Shift+Delete to remove it. If there is none, please just continue with step 3.

3. Manually create a new folder LumionUpdater.

4. In that folder create a new folder: lum23pro.

5. In the folder C:\ProgramData\LumionUpdater\lum23pro save the attached file: update.ini - extract it from the archive.

6. Add exclusions in the antivirus for:

folder: C:\ProgramData\LumionUpdater\
folder: C:\ProgramData\LumionUpdater\lum23pro
file: C:\ProgramData\LumionUpdater\lum23pro\update.ini
file: [lumion installation folder]\update000.exe

Instructions for exclusions:

Knowledge Base: How do you add an exclusion for Lumion in Windows Defender and Windows Firewall?

7. Reboot the PC and start Lumion again.

Let us know how things go and if anything is unclear.

>> ssee attachment:

-----------------------------

3. Unable to complete Update install - looping

If the issue persists, most likely something on your PC is blocking the installation. This is most likely the cause for that is overzealous antivirus/security software. To fix that please try the following:

1. Add an antivirus exclusion for Lumion.exe and the following folder:

·         folder: C:\ProgramData\LumionUpdater\
·         folder: C:\ProgramData\LumionUpdater\lum23pro
·         file: C:\ProgramData\LumionUpdater\lum23pro\update.ini

Knowledge Base: How do you resolve anti-virus and firewall problems?

2. And a firewall exclusion for the same as above. Instructions below:

Knowledge Base: How do you add an exclusion for Lumion in Windows Defender and Windows Firewall?

If you are using different antivirus software, the steps should be similar and easy to look up.

3. After that is done, run Lumion as an Administrator and try to update again.

Let us know how you get on.

Solution:

they were not using an Administrator Windows Account - Admin is required for the Installer (absolute)

We were able to install by signing into our Windows Admin Account.

---

Danny van den Bree 16 March 2023

Yes, you need admin rights to install.

...

Downloading updates on the other hand doesnt need admin.

-------------------------------------------

from Floyd in GChat:

It is possible to disable Lumion updates completely for all user accounts on a computer, by adding a simple registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Lumion\23] "allowUpdates"="false"

When set to false, lumion will bypass the update check completely.

So when the situation arises that admins need to do that for the Updater in their organization then we can advise them directly, on a case by case basis, otherwise this is internal info only.

---

Lumion 2024 (9/05/2024)

this also works - well, tested once

add a String Entry

Edit entry

enter false in value

no Updates notification

Note: if there is no entry - no allowUpdates entry then Lumion takes that as a default Yes to allow Updates

So the user needs to specifically not allow Updates using this entry

-------------------------------------------------

12/08/2023

Myryl Veloso

9:02 AM

https://lumion.zendesk.com/agent/tickets/55978 - ```turn off notifications: yes - see floyd's workaround``` is this the one with the Regedit? -- new -> string value -> name it allowUpdates -- if they want to disable updates, which string value do they need to put?

Peter

46 min

hi, reading

Peter

38 min

, Edited

re see floyd's workaround: will need to find that, Ive not got nay inof on at hand - searching or you got link to ref? generally we should not muck around with regEdit setting Lumion to no updates is all thats needed, but for multi-user for them to do for all already installed? then for an IT they could will need to see if can find info/workaround but in terms of then installing the updates -dont think this is what Dimitris was thinking of though if its regEdit stuff in the IKB notes on the new Installer from Floyd I found and it refreshed my memory for the installer

Of course we hope the new installer won't cause any issues for our users. But if some users are walking into issues, that we can't resolve, we have the inno setup version as backup. In those situations send the suitable v2_dm.exe

https://kb.lumion.com/hc/en-us/articles/4420495628562--DRAFT-Notes-Installer-V2-0-and-new-Updater

However that was when the downloader etc was in its first iteration and since then there have been changes so I doubt that would work

Peter

35 min

, Edited

What is needed is for them to not use the Updater. And then to get the most up to date version, its easy, they download the full version from their Lumion Account and then use the Silent install which will give them everything they need for multi-user install. the only gripe they might have is that they must download the full 26GB all files install and not the much smaller Update files. Tough until dev can create something for the Updater. Make sense?

Peter

29 min

edited my first reply a bit

Myryl Veloso

27 min

alright, thanks Peter 👌

Peter

25 min

I think this ticket reading it now https://lumion.zendesk.com/agent/tickets/55040

Myryl Veloso

23 min

yeah, this one with the turn on/off the updates notification in regedit

Peter

18 min

yep, just trying it now

Peter

11 min

, Edited

hmmm, so that allowUpdates does not do what was expected in that ticket theres ~~another RegEdit~~ or I think it must be a Settings.ini value required all that entry does is include the Setting in Lumion so the user can have that setting in the UI, not the actual value of the setting

Peter

2 min

in any case that setting is only to allow for auto-background updates and for the user in new ticket #55978 they dont need it anyway, as far as I know they have a Group policy that sets user permissions to no installs. updates anyway so the students wont be able to do it themselves even if the Allow Updates UI checkbox is there they could set the RegEdit entry to prevent that Setting in the Settings UI, but given students can update anyway, theres probably no point in giving them all the details unless it became necessary or you can ask them if they want us to provide them also with details on how to not show that setting (so long as its exactly clear what it is used for) and we can do that in a subsequent reply.

---

see this July 2023 ticket and Dimitris reply

https://lumion.zendesk.com/agent/tickets/55040

NEEDS RECHECKING WITH FLOYD OR DANNY - getting confirmations in the Installer v2 Room

This entry is only to allow the Setting to be shown in the Settings UI,

it does not turn the setting on or off

that possibly is done when the user changes it (when it is available in the UI) and is stored in the Settings.ini file

---

There is an option that allows system administrators to turn updates on and off in the Windows registry. It may be a situation where this was attempted.

Let's try the following:
1. Start Menu -> RegEdit -> Right-click and run as Admin:

2. Navigate to: Computer\HKEYLOCALMACHINE\SOFTWARE\Lumion\

3. See if there is a 23 folder under Lumion. If not, create one manually (right-click Lumion -> New -> Key -> name it 23 and hit OK)

4. In the window to the right, right-click the white space -> new -> string value -> name it allowUpdates

5. Once created, double click it -> set it to true and hit OK:

6. It should look like this:

7. Reboot the PC and start Lumion. Does it prompt for an update?

------------==========================

https://lumion.zendesk.com/agent/tickets/53939

for some steps on Uninstaller

====================

Notes on no Updater folders in ProgramFiles folder and Updater cant Update from a prior to current version:+ resolution when sorted

will tidy and drop into a separate IKB for this

TechSupp room Tues 22/08/2023

Javier Prieto

5:40 AM

hey Marius, when is the Lumion Updater folder in ProgramData created? is it when installing, or when starting Lumion for the first time

do you know?

Dimitris Sifakis

5:54 AM

it's when lumion is looking for an update after first run

Marius Giertz

5:54 AM

i’ll get back on that in an hour or so when im back from my walk.

Marius Giertz

6:03 AM

@Javier Prieto got an example full folder path for me? so i know what to look for?

Javier Prieto

6:04 AM

problem is when we suggested adding an exclusion for that folder, the user said it didnt exist

Javier Prieto

6:05 AM

, Edited

so im curious to know what might have prevented its creation - and how

Marius Giertz

6:06 AM

lumion does not create that.

the updater does.

Javier Prieto

6:07 AM

and Lumion tells the updater000.exe to create it when its first run?

Marius Giertz

6:09 AM

on first run of the updater, yes, but, i think it needs some parameters and/or a working license file in order to create the folder.

Marius Giertz

6:10 AM

, Edited

because it needs to know what major version of lumion + if it is norm or pro or student

that first run is usually triggered by lumion

HOWEVER

that only happens if there are pending updates and the user allows it

then there’s also the registry value that disables the updater

Marius Giertz

6:13 AM

, Edited

meaning if that is set to false, or the user always postpones the update/download, lumion will never start the updater

does that make sense?

Javier Prieto

6:23 AM

yep, we already tried creating the registry value manually though

Myryl Veloso

6:23 AM

grabbing lunch guys brb

Javier Prieto

6:23 AM

🤔

its probably their sentinels AV causing trouble

Marius Giertz

6:27 AM

when we suggested adding an exclusion for that folder, the user said it didnt exist if you added the reg value to disable the update them it wont start the updater if user doesnt allow lumion to download the pending updates when prompted, it wont start the updater if there are no pending updates because server says nope, then it wont start the updater. in all 3 scenarios you do not get a folder.

Does user get prompted for updates? and he says yes, download now?

back in 20m.

Javier Prieto

6:30 AM

nope, thats the problem ,they are not getting prompted for updates

so we suggested adding av exclusions for the updater folder > it did not exist

Marius Giertz

6:31 AM

then they are either up to date

Javier Prieto

6:31 AM

so we suggested creating it manually > still did not work

Marius Giertz

6:31 AM

or server says no

Javier Prieto

6:32 AM

then suggested the registry entry allowupdates > still did not work

they are on 23.1.2

Marius Giertz

6:33 AM

brb

error log?

activation key?

Javier Prieto

6:36 AM

they did AV exclusions for the following as well as for Lumion exe and the updater

now I suggested Firewall exclusions but....

jmorgan I don’t think this is the answer, since we have 3 other machines that are updating from office network w/o changes to firewall.

activation key:

THOC6FQI

we dont have an error log

Marius Giertz

6:38 AM

single seat?

hmm unfortunate

Javier Prieto

6:38 AM

, Edited

I requested a logfile.txt but its missing since the updater folder wasn't created

its a 3 seat sub

we have a dxdiag and a .nfo though

what would you look for in an error log?

Marius Giertz

6:39 AM

errors 🤡

almost home

can dig deeper

Javier Prieto

6:41 AM

Marius Giertz

6:44 AM

alright home.

Marius Giertz

6:47 AM

, Edited

error log can verify that the version number of lumion is indeed 23.1.2 error log maybe logs a list of updates from the server - or maybe even an error if there is one. <<- need to verify this. //edit: no on the logging of list, but if there's an internal error it still may be valuable.

Marius Giertz

6:47 AM

, Edited

it might also log if lumion actually starts the updater... //edit: it doesnt log this. But, it does log an error when this fails.

Javier Prieto

6:49 AM

good to know

Ive requested it

Javier Prieto

6:51 AM

grabbing lunch now

Marius Giertz

6:59 AM

so I'll add some extra logging to the lumion side of the updater: https://lumion.atlassian.net/browse/LUMDEV-61076

Myryl Veloso

7:16 AM

back

Marius Giertz

46 min

@Javier Prieto so for a moment I was thinking that the server might be denying that particular lumion based on a key, or number of seats in use, but i'm not sure as it seems to work just fine on my end. I've added the extra debugging info as per the jira issue. If you have a 23.1.2: can you try replacing a cgr manually and see if the updater (and logging) works? Note that this would be a onetime thing for the user and they should restore their cgr after the update works! The cgr will be included in the 23.2.1 update (scheduled for sometime next week)

Lumion\ArchitectEdition\Classes\HomeMode\

Updater.cgr

disclaimer: I have not tested if this works with 23.1.2

arright thats me I'm out.

============================

For info:

this happened to me so logging in case:

installed 23.4.2 to get 2..4.3

confirmed version: